collection

3.1.2.1. CalDAV Client 1

The following are general things noted with our client testing.

  • network communication stopped after receiving a 50x errors.

  • did not treat calendar user addresses as case insensitive (e.g. MAILTO versus mailto).

  • did not send updates for declined meetings when the location is changed

  • did not handle authentication with a username and no password specified for a CalDAV account.

  • did not handle absolute URLs for the calendar home set.

  • did not handle retrieving events with inline attachments.

  • did not gracefully handle CalDAV servers that did not support CalDAV scheduling.

  • did not allow users to setup delegate access without Open Directory support.

  • sent POSTs for an overridden event using a RECURRENCE-ID with different a time zone then the DTSTART of the master event.

The following is a list of server issues that encountered during testing:

  • Invitations were not put into the attendee’s inbox.

  • One CalDAV client tried to set an ACL on a new calendar and received a 501 error.

  • Deleting calendar returned a 409 not a valid resource.

  • Free busy worked on the first calendar but not on additional calendars.

  • Principal URLs don’t work as attendees. Only email addresses worked.

  • Free busy worked on the first calendar but not on additional calendars.

  • Principal URLs don’t work as attendees. Only email addresses worked.

  • did not receive any notifications for invitations or replies because no iTIP messages were placed in the inbox.

  • Re-inviting an attendee to an event did not change the attendee’s PARTSTAT to NEEDS-ACTION.

  • Server removed X-WR-iTIPALREADYSENT from the VEVENT when client does a PUT.

  • not including a METHOD on iTIP messages placed in the INBOX. It appears that when doing a PROPFIND on the inbox, returns ICS data from a calendar instead.

  • A server failed to delete an overridden instance of a recurring meeting.

  • When creating a new calendar, server did not maintain the displayname or calendar-color on the calendar.

  • not including a METHOD on iTIP messages placed in the INBOX.

  • Deleting the fourth instance of a recurring meeting (Test 2.8) failed because server modified the time of the EXDATE.

  • Client tried to modify recurring events and overridden events but occasionally received a “304 not modified”.

  • A server failed to create new calendars.

  • Client tried to delete events but occasionally received 500 errors.

  • Free busy didn’t work for recurring events.

  • client tried to create a new calendar but received a 503 error.

  • A server modified/removed the organizer property on a PUT.

  • Modifications to events immediately after creating them often resulted in the server not properly persisting the change. This made it difficult to proceed with the more advanced tests such as overriding recurring events.

  • Scheduling and FREE/BUSY wasn’t supported on some servers.